Kit for establishing and maintaining communications across disparate networks

ABSTRACT

A system for establishing and maintaining communications across disparate networks comprises a satellite dish and control unit comprising a network management server and a satellite data conversion component. The control unit may further comprise an application server and a satellite dish alignment component. The system may further comprise at least one access point and a plurality of wireless routers. In certain embodiments, the system is relatively easy to deploy and can even be used when traditional network infrastructure is unavailable.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.11/383,899, filed May 17, 2006, titled SYSTEM AND METHOD FORESTABLISHING AND MAINTAINING COMMUNICATIONS ACROSS DISPARATE NETWORKS,that claims priority under 35 U.S.C. §119(e) of U.S. Provisional PatentApplication No. 60/754,120, filed Dec. 27, 2005, titled MOBILE SATELLITETCP/UDP/IP WIRELESS & WIRED TACTICAL NETWORK COMMAND AND CONTROL, whichapplication is incorporated by reference in this application in itsentirety.

FIELD OF THE INVENTION

The present invention relates to systems adapted for communicationacross disparate networks and more particularly to systems forestablishing communication across such networks in the absence of fixednetworking infrastructure.

BACKGROUND

Existing networking solutions work well when fixed infrastructureprovides the necessary power and network connectivity to users inrelatively fixed locations. But for mobile network users such as firstresponders, law enforcement officers and other emergency personnel,known networking solutions do not necessarily provide the same reliablebroadband network connectivity. Particularly with environmentaldisasters, such as hurricanes, chemical spills, floods, and the like,when fixed network infrastructure may be damaged or inaccessible, theability to reliably send and receive voice and video communications,text messages, and other data is important.

There is a need for a reliable, portable and quickly deployable solutionfor coordination and linking of various wireless and wired broadbandnetworks “in the field”—particularly one that can securely andseamlessly transmit data to and from network users, even if they are ina “scorched earth” environment. Ideally, this solution need not dependon access to network infrastructure and would be independent of networktopology, having the ability to transparently integrate with mobile,fixed, mesh, and structured network environments, using variousnetwork-configurable protocols. It would also be advantageous if thissolution could be installed or set up by a user without networkingexpertise.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain embodiments of the present invention are illustrated by theaccompanying figures. It should be understood that the figures are notnecessarily to scale and that details not necessary for an understandingof the invention or that render other details difficult to perceive maybe omitted. It should be understood, of course, that the invention isnot necessarily limited to the particular embodiments illustratedherein.

FIG. 1 is a network diagram illustrating disparate networks formed inaccordance with one embodiment of the present invention.

FIG. 2A is a system diagram illustrating a front perspective view ofcomponents utilized in forming the network of FIG. 1.

FIG. 2B is an exploded front perspective view of a control unit shown inFIG. 2A.

FIG. 2C is a rear view of the control unit of FIG. 2B.

FIG. 2D illustrates the connections between various components in thesystem of FIG. 2A.

FIG. 3 illustrates the software components residing on the networkmanagement and application servers of FIGS. 2A-2D.

FIG. 4 is a flow chart illustrating the steps for sending communicationsfrom a wireless client using the system of FIG. 2A.

FIG. 5 is a flow chart illustrating the steps for sending communicationsfrom a wired client using the system of FIG. 2A.

FIG. 6 is a flow chart illustrating the steps for establishing andsending communications over a virtual private network using the systemof FIG. 2A.

DETAILED DESCRIPTION

A system enables the exchange of data, voice and video securely acrossdisparate networks, even when traditional network infrastructure isunavailable, damaged or inaccessible. In one embodiment, a control unitcomprising a network management server, allows users to communicateacross a plurality of sub-networks, including private networks, such aswired and wireless networks within a local area and public networks likethe Internet. Users can also communicate over a virtual private network(“VPN”), via the Internet. In the event of a nature disaster, where celltowers, public switched telephone network and power lines are down, thesystem can be deployed to establish a local area network for wired andwireless users alike. The system can be configured and deployed for userapidly, between about 10.0 minutes and about 40.0 minutes, 20.0 minutesto about 40.0 minutes and more particularly between about 10.0 minutesand 20.0 minutes for example.

As shown in FIG. 1, the system provides communication and servicesbetween various network communication devices across both private andpublic networks 102 and 104. The system establishes a local area privatenetwork 102 comprising wireless and/or wired sub-networks 106 and 108.Wireless sub-network 106 may comprise a mesh network and a logicalwireless network for communication over Ethernet connections.

A mesh network is a network that routes data between nodes in theabsence of a centralized server used for authentication, withself-authentication occurring between nodes in the network. Meshnetworks provide continuous connections and reconfiguration aroundblocked paths by hopping from node to node in the most efficient pathpossible (by searching for the shortest path between two points) untilconnections can be established. Mesh networks are self healing, whichmeans that the network can still operate even when a node or otherconnection is inoperable. Each node within the network authenticates theothers. The nodes may, for example, be network communication devices,routers or network access points.

Each of wireless and wired sub-networks 106 and 108 may be designatedwith its own IP address space. For example, wireless sub-net 106 may bedesignated with 10.0/16 addresses and wired sub-net 108 may bedesignated with 192.168/16 addresses.

Wired and wireless users within the wireless and wired networks 106 and108 can advantageously communicate with one another across virtually anynetwork protocol, including without limitation Transmission ControlProtocol/Internet Protocol (TCP/IP), User Datagram Protocol (UDP),Internet Packet Exchange (IPX), Sequenced Packet Exchange (SPX), etc. Inaddition, these users can quickly gain access to the Internet and usethe Internet to communicate over a VPN.

FIG. 2A illustrates one embodiment of the system 200 of the presentinvention, which comprises control unit 202, access point 204, satellitedish 206 and network communication devices 208. The system may furthercomprise a plurality of wireless routers 210.

With reference to FIG. 2A-2D, control unit 202 may comprise networkmanagement server 212, application server 214, switch 215, input device216, monitor 218 comprising display screen 220, satellite dish alignmentcomponent 222, satellite data conversion component 224, patch panel 226comprising various connection ports hard wired into network managementand application servers 212 and 214 and power strip 250. As describedhereinafter, various connection cables, such as Ethernet cables, connectcertain components within system 200 to one another.

The foregoing components of control unit 202 are typically mounted in asingle rugged plastic case 221 and powered up through connection ofpower cable 250 to power source 252, such as a generator. The singlerugged case may comprise dimensions between about 15.0 inches to about25.0 inches in height, about 20.0 inches to about 30.0 inches in widthand about 30.0 to about 40.0 inches in length. The case may comprise apull-out rack for mounting the various components. One embodiment ofcase is available from Hardigg Industries, Inc. of South Deerfield,Mass. With the components mounted in the case, control unit typicallyweighs between about 100.0 pounds to about 200.0 pounds and moreparticularly between about 150.0 pounds to about 200.0 pounds. Thus,case 221, with control unit 202 positioned therein may be man-portable(capable of being physically carried by one to three men). Accordingly,control unit 202 may be packaged in a kit with instructions forassembling the system. The kit may comprise all or select components ofcontrol unit 202.

Network management server 212 is a device capable of managing androuting communications across disparate networks. Network managementserver 212 may comprise various network management and servicesub-processes, described hereinbelow as well as certain networkinterface ports, including wired network interface 205 for communicationwith wired sub-network 108, wireless network interface 207 forcommunication with wireless sub-network 106 and Internet networkinterface 209 for communication with the Internet, via satellite dish206. User may connect various wired devices to wired network interface,including computers, phones and the like. Network management server 212may be a multi-purpose server running on a Linux operating system. TheLinux operating system enables communication over different networkprotocols, including those network protocols listed above.

Application server 214 may operate on a windows based operating systemand typically resides on wireless sub-network 106, with its own IPaddress. Application server 214 comprises four port switch 211, whichconnects in various ways to front and rear ports on patch panel 226 andto access point 204 for wireless sub-network 106 access. Applicationserver 214 may further comprise various application sub-processes.

Switch (hidden from view) is used to control network management andapplication servers 212 and 214 with a single keyboard, monitor andmouse. Switch may be a keyboard video mouse switch (“KVM switch”).Alternatively, switch 215 may accomplish the same purpose throughsoftware that forwards the necessary input over standard networkconnections. Suitable examples include Synergy and MaxiVista availablefrom Bartels Media.

Satellite dish alignment component 222 works in conjunction withsatellite data conversion component 224 to align satellite dish 206 witha satellite (not shown) and convert the satellite signal into a usableprotocol by system 200. The satellite provides a connection to theInternet. Satellite dish alignment component 222 typically comprises aLinux based computer with global positioning software and satellite dishport 243. One example is the alignment system available from TracStarSystems, Inc. of Orlando, Fla. Satellite data conversion component 224can function like a TCP/IP standards compliant bridge, providing aninterface between the satellite and the Internet. In essence, dataconversion component 224 converts data received on an Ethernet port intoa radio-frequency format for sending to the satellite. Satellite dataconversion component 224 may be a Tachyon indoor unit (IDU), availablefrom Tachyon Networks, Inc. of San Diego, Calif.

Access point 204, comprising antenna 203, is adapted to provide networkcommunication devices 208 within its coverage area access to wirelessand wired network services, serving as the principal network managementinterface to associated network communication devices 208 and wirelessrouters 210. In one embodiment, the term access point, as used herein,means a bridge between the wired and wireless networks. Access point 204may also serves as a bridge between radio-frequency based communicationsand Ethernet based communications. In general, access point 204comprises a first network interface card for radio-frequencytransmissions—for example a mesh network memory card to communicate overa mesh network—and a second network interface card to communicate overEthernet connections. In one embodiment, access point 204 is an IAP7300Intelligent Access Point available from Motorola, Inc. of Schaumberg,Ill., which contains two or more 802.11 compliant radios and two or moremesh mobile broadband radios. In one embodiment, one set of radiosoperates in the unlicensed, 2.4 GHz band and the other set operates inthe licensed, 4.9 GHz public safety band.

Instead of permanently affixing access point 204 on top of water towers,radio towers or light poles, it may be placed on tripod 236 for tacticaldeployment and ease of redeployment without dissolution of networks 102and 104. Tripod 236 may be a four meter mast system rated to withstandup to 120 m.p.h. wind loads.

Satellite dish 206 may be auto-deployed to provide Internet access fortemporary field locations, emergency response teams and special events.Dish 206 may be deployed within about two to three minutes. Oneembodiment of satellite dish 206 is available from Tachyon Networks,Inc. This embodiment automatically aligns with an airborne satellitethrough satellite dish alignment component 222. Satellite dish 206 mayalso be manually aligned with satellite, though this process takesadditional time to properly deploy. Satellite dish may be mounted on aplatform comprising wheels for ease of deployment and transport.

Network communication devices 208 may be laptop computers, personalcomputers (PC), wireless telephones, personal digital assistants (PDA),video cameras, or any other device capable of receiving and/ortransmitting voice, video or data. In one embodiment, for example,wireless analog phones run in the 900 MHz or 5.8 GHz range, with basereceiving stations and chargers located in a hardened case connected toa wireless element to communicate across the network. The case maycomprise connectors for power and data cables, for connection to patchpanel 226. In another embodiment, portable laptop computers comprisecommunication software application described in co-pending, co-ownedU.S. patent application Ser. No. 11/383,775, entitled “Apparatus andMethod for Dynamically Updating and Communicating Within FlexibleNetworks,” of Dumas, et al., the entire disclosure of which is herebyincorporated by reference. These portable laptop computers cancommunicate over wireless sub-network 106 through mesh enabled networkcommunication architecture.

The system may further comprise a plurality of wireless routers 210.Routers 210 may be strategically placed to increase network coverage inlarge geographic areas. Through the use of routing tables, routers 210allow communications to travel in the most efficient manner from onepoint to another within wireless network 106. Use of routers 210advantageously provides users with the capability of tapping into afully enabled and scalable mesh network, with authentication at therouter 210 level.

A plurality of Ethernet cables may be utilized to establish connectionsamong the components and networks within system 200. Generally,speaking, the connections provide a path for data between applications,servers and the Internet. Although such connections may be configured invarious ways, a preferred framework is illustrated in FIG. 2D anddescribed hereinafter. Referring now to FIG. 2D, patch panel 226comprises a plurality of front and rear ports, with each front portelectrically connected to a corresponding rear port. Specifically, patchpanel 226 comprises front and rear application server ports 227 and 229,first front and rear phone port 231 and 233, second front and rear phoneports 235 and 237, front and rear access point ports 239 and 241, andfront and rear network management server ports 244 and 245.

Front application server port 227 connects to four port switch 211 whilerear application server port 229 connects to wireless network interface207 on network management server 212. In this way, application server214 connects to wireless network 106 for sending and receipt of dataover Ethernet connections.

First and second front phone ports 231 and 235 connect to base stationsof network communication devices 208 used in the field. First and secondrear phone ports 233 and 237 connect to four port switch 211. Theseconnections enable communication over wireless network 106.

Front access point port 239 connects to access point 204, while rearaccess point port 241 connects to four port switch 211. The connectionof access point 204 to control unit 202 in this way enables conversionof radio frequency based communications into Ethernet basedcommunications for transmission of data over wireless network 106.

Front management server port 244 connects to Internet network interfaceport 209 on network management server 212 while rear management serverport 245 connects to satellite dish port 243 on satellite dish alignmentcomponent 222. These connections are used for communications over theInternet.

As shown in FIG. 3, network management server 212 comprises networkmanagement server process 300, which comprises various networkmanagement sub-processes 302, including firewall process 304 and routingprocess 306 as well as various service-based sub-processes 303including, VPN authentication process 307, VPN interface process 308,dynamic host configuration protocol (“DHCP”) process 310, domain namingsystem (“DNS”) process 312 and web server process 314. Firewall process304 filters unwanted incoming and outgoing communications from controlunit 202, typically by validating that the source address corresponds tothe particular network on which the communication was received and onlyallowing specific port numbers from the internet. Routing process 306directs communications to the appropriate network interface. VPNauthentication process 307 determines whether VPN clients are permittednetwork users. VPN interface process 308 provides a connection orinterface to Internet for virtual private network connectivity. DHCPprocess 310 dynamically assigns IP addresses to devices on the network.DNS process 312 transforms a host name, such as an Internet UniformRecord Locator (URL), into an IP address by accessing the host via thesatellite link. By caching the retrieved IP address locally, DNS process312 decreases traffic over the satellite link when subsequent requestsfor the same host are made. Web server process 314 stores and providesinformation to network communication devices within the local areanetwork (e.g., list of local telephone numbers). Network managementserver 212 may also comprise Mesh manager software for communicatingover the mesh network.

Application server 214 may also comprise various application processes.Examples include video and audio sub-processes for video and audiocommunication and file transfer sub-process for transferring fileswithin the networks.

Having described the components of system 200, we turn now to thestepwise sequence for assembly of system 200. As previously mentioned,system 200 is capable of being assembled with 10-40 minutes. Controlunit 202 is positioned on a flat sturdy surface such that the operatorhas access to its front and rear. (At this point, the connectionsbetween the various ports on patch panel 226, network management andapplication servers 212 and 214 and access point 204 are alreadyestablished). A power cable for control unit 202 is plugged into powerstrip 250 connected to a power generator 252, such as an AC powersource. Satellite dish 206 is positioned on a level surface in alignmentwith the approximate location of a Geosynchronous satellite. Connectioncables are secured to satellite dish 206 and appropriate locations oncontrol unit 202. If phones are being used, other connection cables,such as Ethernet Cat-5 cables, can be used to connect the phones tofirst and second front phone ports 231 and 235 within patch panel 226.Tripod 236 is set up and access point 204 positioned on top thereof.Antenna 203 is connected to access point 204 and connection cables(Ethernet Cat-5) are secured to access point 204 and front access pointport 239. Power cables connect access point 204 to power strip 250 orthe AC power source. Control unit 202 is started by powering on networkmanagement and application servers 212 and 214 as well as satellite dishalignment component 222. Input device 216 and monitor 218 are pulled outof case and locked into position.

After assembly of system 200, communication across the disparatesub-nets may occur. Prior to communication, however, clients aretypically authenticated. Clients operating in the wired and wirelessnetwork, for example, are authenticated through access point 204 orwireless router 210. Each individual client forwards its media accesscontrol (“MAC”) addresses to access point 204 along with a request forDHCP services to network management server 212. If the MAC addresses arerecognized, access point 204 informs network management server 212,which forwards an IP address back through access point 204 and on to theclient. If the client is a VPN user, a request for authentication issent to network management server 212, where VPN authentication process307 determines whether the client is a permitted user. VPNauthentication may occur in various ways, via static keys, username andpassword, etc.

Once clients have been authenticated, communication adheres to a generalframework that may be adjusted depending on the source/destination andnature of the communication being sent. Generally, the destinationclient of the communication is determined as one of the first steps. Ifthe destination client employs the same type of device as the sourceclient, the communication is routed directly thereto without travelingthrough network management server 212. Otherwise, the communication issent to network management server 206, where firewall process 304filters it according to the firewall rules in place. Router process 306then directs the communication to the appropriate network interface forreceipt by the destination client. Depending on the nature of thecommunication, the destination may respond through control unit 202 in asimilar manner.

FIG. 4 illustrates the steps for sending communications from a wirelessclient using system 200. In step 402, the wireless client sends acommunication packet to a specified location. The ultimate destinationand nature of the communication packet govern next steps.

In step 404, the system ascertains whether the communication packet isaddressed to another wireless client in the network. If so, in step 406,the communication packet is routed directly to that client or throughanother wireless client in the network. The receiving client, in step408, optionally sends a response back. If the communication packet isnot addressed to a wireless client, the system checks to see if thecommunication packet is addressed to a wired client (step 410), theInternet (step 412) or includes a request for a service by control unit202 (step 414).

If the communication packet is addressed to a wired client, it is sentto control unit 202, where, in step 416, firewall process 304 filtersthe communication packet. In particular, firewall process 304 verifiesthat the source and destination IP addresses correspond to theparticular network on which the communication was received and processesa set of configurable rules based on IP address, port protocol,application, etc. In step 418, routing process 306 routes thecommunication packet to the wired network interface, typically anEthernet port connected to the wired network. In step 420, the wiredclient receives the communication packet and optionally sends back aresponse, which begins the process anew.

If the communication packet is addressed to the Internet (e.g., a mailserver or URL), in step 422, it is sent to control unit 202 wherefirewall process 304 checks the IP address of its source. Since theultimate destination on the Internet is not always known, firewallprocess does not necessarily check the destination IP address. In step424, routing process 306 routes the communication packet to Internetgateway network interface 209, typically an Ethernet port connected tothe Internet. In step 426, the communication packet is routed throughthe Internet to its destination. More specifically, the packet is routedthrough satellite data conversion component 224 and up to the airbornesatellite for connectivity to the Internet. In step 428, a response fromthe Internet is sent back to Internet network interface 209 viasatellite data conversion component 224 so firewall process 304 canensure that the destination of the response corresponds to theparticular network on which the communication was received. In step 430,routing process 306 routes the response to the wireless networkinterface for receipt by the wireless client.

If the communication packet comprises a request for services by networkmanagement server 212, in step 432, firewall process 304 checks thesource IP address. In step 434, one of the service-based sub-processes303 performs the requested service. In step 436, a response is sentthrough the firewall filters, to verify the IP address of thedestination within the network, and on to wireless network interface 207for receipt by the destination that initially sent the request.

FIG. 5 illustrates the steps for sending communications from a wiredclient using system 200. In step 502, the wired client sends acommunication packet to a specified location. Once again, the ultimatedestination and nature of the communication packet govern next steps.

In step 504, the system ascertains whether the communication packet isaddressed to another wired client in the network. If so, in step 506,the communication packet is routed to that client within the network.The receiving wired client, in step 508, optionally routes a responseback. If the communication packet is not addressed to a wired client,the system checks to see if the communication packet is addressed to awireless client (step 510), the Internet (step 512) or includes arequest for a service by control unit 202 (step 514).

If the communication packet is addressed to a wireless client, it issent to control unit, where, in step 516, firewall process 304 filtersthe communication packet. Here again, firewall process 304 verifies thatthe source and destination IP addresses correspond to the particularnetwork on which the communication was received. In step 518, routingprocess 306 routes the communication packet to wireless networkinterface 207, typically an Ethernet port corresponding and connected towireless network 106. In step 520, the wireless client receives thecommunication packet and optionally sends back a response, which beginsthe process anew.

If the communication packet is addressed to the Internet (e.g., a mailserver or URL), in step 522, it is sent to control unit 202 wherefirewall process 304 checks the source IP address. Prior to sending, theoriginator of the packet will probably have retrieved the destinationaddress through a DNS lookup, which will be fulfilled by control unit202 via DNS process 312. The DNS request will be fulfilled from a localcache if possible, limiting traffic to local network. In step 524,routing process 306 routes the communication packet to Internet gatewaynetwork interface 209, typically an Ethernet port corresponding andconnected to the Internet. In step 526, the communication packet isrouted through the Internet to its destination. More specifically, afterreceipt by network interface 209, the packet is routed up to thesatellite for connectivity to the Internet. In step 528, a response fromthe Internet is sent back to Internet network interface 209 and firewallprocess 304 ensures that the destination of the response isauthenticated. In step 530, the response is sent to wired networkinterface 205, for receipt by the wired client.

If the communication packet comprises a request for services by networkmanagement server 212, in step 532, firewall process 304 verifies thatthe source IP address corresponds to the particular network on which thecommunication was received. In step 534, one of the service-basedsub-processes 303 performs the requested service. In step 536, aresponse is sent through the firewall process 304, and on to wirednetwork interface 205 for receipt by the client that initially sent therequest.

FIG. 6 illustrates the steps for sending communications over a virtualprivate network. In step 602, a client, such as a client within wirelessor wired sub-nets 106 and 108 or a client outside the local areanetwork, is authenticated by VPN authentication process 307 on networkmanagement server 210. In step 604, the client sends a communication toVPN interface process 308, also residing on network management server210. The system checks to see if the communication packet is addressedto a wired client (step 605), a wireless client (step 609) or anotherVPN client (step 611) or includes a request for a service by controlunit 202 (step 607).

If wired network 108 is the destination, in step 606, firewall process304 filters the communication by ensuring that the IP addresses of thesource and the destination correspond to the particular network on whichthe communication was received. In step 608, routing process 306forwards the communication to the wired network interface. In step 610,the wired client receives the communication and can respond. In step612, firewall process 306 filters the response by checking the IPaddresses of the source and destination. The response is forwardedthrough VPN interface process 308 for receipt by the client.

If wireless network 106 is the destination, in step 616, firewallprocess 304 filters the communication. In step 618, routing process 306forwards the communication to wireless network interface 207. In step620, the wireless client receives the communication and may respond tothe VPN client. In step 622, firewall process 304 filters the response.The response is forwarded through the VPN interface process 308 forreceipt by the VPN client.

If the communication comprises a request for services by networkmanagement server 212, in step 626, firewall process 304 ensures thatthe source IP address corresponds to the particular network on which thecommunication was received. In step 628, one of service-basedsub-processes 303 performs the requested service. In step 630, aresponse is filtered through firewall process 304, to verify the IPaddress of the destination corresponds to the particular network onwhich the communication was received. The response is forwarded throughVPN interface process 308 for receipt by the VPN client.

If the destination is another VPN client, in step 634, firewall process304 filters the communication by confirming that the source anddestination IP addresses corresponds to the particular network on whichthe communication was received. In step 636, routing process 306 routesthe communication to VPN interface process 308, which, in turn, routesthe communication through the Internet to its destination in step 638.In step 640, a response is sent back through the Internet and ultimatelyfiltered by firewall process 304 in step 642. The response is forwardedthrough VPN interface process 308 for receipt by the VPN client.

Variations, modifications and other implementations of what is describedherein will occur to those of ordinary skill in the art withoutdeparting from the spirit and scope of the invention. For example, fourport switch 211 may reside on other components within system, includingnetwork management server 212. Accordingly, the invention is in no waylimited by the preceding illustrative description.

1. A kit for establishing and maintaining communications acrossdisparate networks comprising: a network management server comprising awireless network interface, a wired network interface and an Internetnetwork interface, the network management server comprising a firewallprocess for filtering incoming and outgoing communications and a routingprocess for routing communications to at least a wireless network, awired network and the Internet through the wireless network interface,the wired network interface and the Internet network interface; and asatellite data conversion component in communication with the networkmanagement server, the satellite data conversion component adapted toconvert data received from the wireless network into a formatrecognizable by a satellite and wherein the network management server isoperable in the absence of a fixed network infrastructure upon in-fielddeployment.
 2. The kit of claim 1, further comprising an applicationserver comprising a plurality of application sub-processes includingvideo and audio sub-processes for video and audio communication and filetransfer sub-process for transferring files over the disparate networks.3. The kit of claim 1, further comprising a satellite dish alignmentcomponent, wherein the satellite data conversion component and thesatellite dish alignment component are connected to the networkmanagement server.
 4. The kit of claim 1, further comprisinginstructions for using the kit in a system for establishing andmaintaining communications across disparate networks.